Configure GigaVUE Fabric Components in AWS

You can use your own AWS orchestration system to deploy GigaVUE fabric nodes (G-vTAP Controller and G-vTAP Agent) and use GigaVUE-FM to configure the advanced features supported by these nodes. These nodes register itself with GigaVUE-FM using the information provided by your AWS orchestration system. Once the nodes are registered with GigaVUE-FM, you can configure monitoring sessions and related services in GigaVUE-FM. Health statistics of the registered nodes are determined by the heartbeat messages sent from the respective nodes.

Note:  Deployment of GigaVUE fabric components through a third-party orchestrator is supported only on Linux platforms. Refer to Linux G-vTAP Agent Installation for detailed information.

In your AWS EC2, you can configure the following GigaVUE fabric components:

Configure G-vTAP Controller in AWS

You can configure more than one G-vTAP Controller in a monitoring domain.

To configure GigaVUE fabric components in AWS platform:

  1. Before configuring GigaVUE fabric components through AWS, you must create a monitoring domain in GigaVUE-FM. While creating the monitoring domain, select G-vTAP as the Traffic Acquisition Method. Refer to Create a Monitoring Domain for detailed instructions.

    Note:  You can use AWS Orchestrator for GigaVUE fabric node configuration only using V Series 2 nodes.

  2. In the AWS Fabric Launch Configuration page, select No for the Configure a G-vTAP Controller field as you are going to configure the G-vTAP Controller in AWS Orchestrator.
  3. Configure V Series Proxy, V Series nodes, and save the Fabric launch configuration. Refer to Configure GigaVUE Fabric Components in GigaVUE-FM for detailed instructions. You can find the deployed GigaVUE fabric nodes in the Instances page on your Amazon EC2.
  4. In your AWS environment, launch the G-vTAP Controller AMI instance using any of the following methods:

    Register G-vTAP Controller using AWS GUI

    To register G-vTAP Controller using the user data in AWS GUI:

    1. On the Instances page of AWS EC2, click Launch instances. The Launch Instance wizard appears. For detailed information, refer to Launch an instance using the Launch Instance Wizard topic in Amazon EC2 Documentation.
    2. On the Step 3: Configure Instance Details tab, enter the User data as text in the following format and deploy the instance. The G-vTAP Controller uses this user data to generate config file (/etc/gigamon-cloud.conf) used to register with GigaVUE-FM.
      #cloud-config
      write_files:
       - path: /etc/gigamon-cloud.conf
       owner: root:root
       permissions: '0644'
       content:
           Registration:
      	groupName: <Monitoring Domain Name>
      	subGroupName: <Connection Name>
      	user: orchestration
      	password: orchestration123A!
      	remoteIP: <IP address of the GigaVUE-FM>
      	remotePort: 443
      You can navigate to Instances > Actions > Instance Settings > Edit user data and edit the user data.

    The G-vTAP Controller deployed in AWS EC2 appears on the Monitoring Domain page of GigaVUE-FM.

    Register G-vTAP Controller using a configuration file

    To register G-vTAP Controller using a configuration file:

    1. Log in to the G-vTAP Controller.
    2. Edit the local configuration file (/etc/gigamon-cloud.conf) and enter the following user data.
      Registration:
      	groupName: <Monitoring Domain Name>
      	subGroupName: <Connection Name>
      	user: orchestration
      	password: orchestration123A!
      	remoteIP: <IP address of the GigaVUE-FM>
      	remotePort: 443
    3. Restart the G-vTAP Controller service.
      $ sudo service gvtap-cntlr restart

    The deployed G-vTAP Controller registers with the GigaVUE-FM. After successful registration GigaVUE-FM returns heartbeats in the time interval of 30 seconds. If one heartbeat is missing , G-vTAP Controller status appears as 'UnHealthy'. If more than three heartbeats fail to reach GigaVUE-FM, G-vTAP Agent will be marked as 'Unknown'. If more than three heartbeats fail to reach GigaVUE-FM, G-vTAP Controller will be marked as 'Down'.

Configure G-vTAP Agent in AWS

G-vTAP Agent should be registered via the registered G-vTAP Controller and communicates through PORT 8891.

Deployment of G-vTAP Agents through third-party orchestrator is supported on Linux and Windows platforms.

To register G-vTAP Agent using a configuration file:

  1. Install the G-vTAP Agent in the Linux or Windows platform. For detailed instructions, refer to Linux G-vTAP Agent Installation and Windows G-vTAP Agent Installation.

  2. Log in to the G-vTAP Agent.
  3. Edit the local configuration file and enter the following user data.
    • /etc/gigamon-cloud.conf is the local configuration file in Linux platform.
    • C:\ProgramData\gvtap-agent\gigamon-cloud.conf is the local configuration file in Windows platform.

    Registration:
    	groupName: <Monitoring Domain Name>
    	subGroupName: <Connection Name>
    	user: orchestration
    	password: orchestration123A!
    	remoteIP: <IP address of the G-vTAP Controller 1>, 
		   <IP address of the G-vTAP Controller 2>
    	remotePort: 8891
  4. Restart the G-vTAP Agent service.
    • Linux platform: 
      $ sudo service gvtap-agent restart
    • Windows platform: Restart from the Task Manager.

Note:  You can configure more than one G-vTAP Controller for a G-vTAP Agent, so that if one G-vTAP Controller goes down, the G-vTAP Agent registration will happen through another Controller that is active.

The deployed G-vTAP Agent registers with the GigaVUE-FM through the G-vTAP Controller. After successful registration GigaVUE-FM returns heartbeats in the time interval of 30 seconds. If one heartbeat is missing, G-vTAP Agent status appears as 'Unhealthy'. If more than five heartbeats fail to reach GigaVUE-FM, G-vTAP Agent will be unregistered from GigaVUE-FM.

To view the registered G-vTAP Agents in GigaVUE-FM, on the Monitoring Domain page, click G-vTAP Agents. The G-vTAP Agents page appears with the list of registered agents.